Universal Peer-to-Peer Signaling Network Virtualization and Orchestration

ABSTRACT

Concepts and technologies disclosed herein are directed to universal peer-to-peer signaling network virtualization and orchestration. According to one aspect of the concepts and technologies disclosed herein, a universal DIAMETER orchestrator can determine DIAMETER peer nodes to be utilized to handle DIAMETER signaling traffic for a service. The universal DIAMETER orchestrator can allocate transport resources over which a transport connection between the DIAMETER peer nodes can be established. In some embodiments, the universal DIAMETER orchestrator can allocate the transport resources on-demand. The universal DIAMETER orchestrator can allocate DIAMETER resources to provision DIAMETER signaling interfaces to handle the DIAMETER signaling traffic between the DIAMETER peer nodes. In some embodiments, the universal DIAMETER orchestrator can allocate the DIAMETER resources in accordance with a rule to override a traditional DIAMETER routing agent.

CROSS-REFERENCE FOR RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 15/143,401, entitled “Universal Peer-to-PeerSignaling Network Virtualization and Orchestration,” filed on Apr. 29,2016, now allowed, which is incorporated herein by reference in itsentirety.

BACKGROUND

The signaling network is of vital importance to network serviceproviders. This is because the signaling network directs signalingtraffic from source to destination leveraging Third GenerationPartnership Project (“3GPP”) standard protocols, such as DIAMETER andRADIUS. DIAMETER protocol is an authentication, authorization, andaccounting (“AAA”) protocol that works at the application layer of theOpen Systems Interconnection (“OSI”) model. DIAMETER supersedes RADIUSand provides several new features, including application layeracknowledgement, capability negotiation, and extensibility to add newfeatures. DIAMETER is a message-based protocol, whereby end pointsexchange messages and receive positive or negative acknowledgements.DIAMETER protocol is well-documented in technical specifications such asthose available from the Internet Engineering Task Force (“IETF”),particularly Request for Comments (“RFC”) 6733 and related documents.

Protecting and maintaining the signaling network is critical to avoidnetwork outages and to promptly deliver a wide range of revenuegenerating services, including, for example, video, social network,social media, Voice over Long-Term Evolution (“VoLTE”), e-commerce,multimedia, and messaging. The signaling network must operate properlyand must not become overloaded to avoid network outages. When thesignaling network becomes overloaded, a registration storm can betriggered and cause both the signaling network and the bearer network tostop functioning or to function at a reduced capacity.

SUMMARY

Concepts and technologies disclosed herein are directed to universalpeer-to-peer signaling network virtualization and orchestration.According to one aspect of the concepts and technologies disclosedherein, a universal DIAMETER orchestrator can determine DIAMETER peernodes to be utilized to handle DIAMETER signaling traffic for a service.The universal DIAMETER orchestrator can allocate transport resourcesover which a transport connection between the DIAMETER peer nodes can beestablished. In some embodiments, the universal DIAMETER orchestratorcan allocate the transport resources on-demand. The universal DIAMETERorchestrator can allocate DIAMETER resources to provision DIAMETERsignaling interfaces to handle the DIAMETER signaling traffic betweenthe DIAMETER peer nodes. In some embodiments, the universal DIAMETERorchestrator can allocate the DIAMETER resources in accordance with arule to override a traditional DIAMETER routing agent.

In some embodiments, the universal DIAMETER orchestrator can receive aservice request from a user equipment (“UE”) device. The service requestcan specify the service to be provided to the UE device. The universalDIAMETER orchestrator can analyze the service request to identify theservice.

In some embodiments, the universal DIAMETER orchestrator can determineone or more DIAMETER applications to be utilized to meet a DIAMETERsignaling requirement of the service. In some embodiments, the universalDIAMETER orchestrator can create a structured representation of DIAMETERapplication data associated with the DIAMETER application(s). Theuniversal DIAMETER orchestrator also can report the structuredrepresentation. The structured representation can be formatted inJavaScript Object Notation (“JSON”).

In some embodiments, the universal DIAMETER orchestrator can analyze astructured DIAMETER protocol stack at a DIAMETER applicator layer, atransport layer, and an IP layer to ensure that the transport resourcesare allocated to meet the DIAMETER signaling requirement for theservice.

In some embodiments, the universal DIAMETER orchestrator can map theDIAMETER resources available in a network designed to provide theservice.

It should be appreciated that the above-described subject matter may beimplemented as a computer-controlled apparatus, a computer process, acomputing system, or as an article of manufacture such as acomputer-readable storage medium. These and various other features willbe apparent from a reading of the following Detailed Description and areview of the associated drawings.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intendedthat this Summary be used to limit the scope of the claimed subjectmatter. Furthermore, the claimed subject matter is not limited toimplementations that solve any or all disadvantages noted in any part ofthis disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a network operating environmentin which aspects of the concepts and technologies disclosed herein canbe implemented.

FIG. 2 is a block diagram illustrating a DIAMETER protocol stack capableof being utilized to implement aspects of the embodiments presentedherein.

FIG. 3 is a block diagram illustrating a traditional configuration forDIAMETER orchestration in accordance with prior implementations.

FIG. 4 is a block diagram illustrating a configuration for DIAMETERorchestration, according to an illustrative embodiment.

FIG. 5 is a block diagram illustrating a method for DIAMETERorchestration, according to an illustrative embodiment.

FIG. 6 is a block diagram illustrating an example mobile device capableof implementing aspects of the embodiments disclosed herein.

FIG. 7 is a block diagram illustrating an example computer systemcapable of implementing aspects of the embodiments presented herein.

FIG. 8 is a block diagram illustrating an example network functionsvirtualization platform (“NFVP”) capable of implementing aspects of theembodiments presented herein.

DETAILED DESCRIPTION

While the subject matter described herein may be presented, at times, inthe general context of program modules that execute in conjunction withthe execution of an operating system and application programs on acomputer system, those skilled in the art will recognize that otherimplementations may be performed in combination with other types ofprogram modules. Generally, program modules include routines, programs,components, data structures, computer-executable instructions, and/orother types of structures that perform particular tasks or implementparticular abstract data types. Moreover, those skilled in the art willappreciate that the subject matter described herein may be practicedwith other computer systems, including hand-held devices, mobiledevices, wireless devices, multiprocessor systems, distributed computingsystems, microprocessor-based or programmable consumer electronics,minicomputers, mainframe computers, routers, switches, other computingdevices described herein, and the like.

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and in which are shown byway of illustration specific embodiments or examples. Referring now tothe drawings, in which like numerals represent like elements throughoutthe several figures, aspects of concepts and technologies for universalpeer-to-peer signaling network virtualization and orchestration will bedescribed.

Turning now to FIG. 1, a block diagram illustrating an operatingenvironment 100 in which aspects of the concepts and technologiesdisclosed herein can be implemented. The operating environment 100includes a plurality of user equipment devices (“UEs”) 102A-102N(referred to herein collectively as UEs 102, or in the singular form asUE 102) operating in communication with a radio access network (“RAN”)104. Each of the UEs 102 can be a cellular phone, a feature phone, asmartphone, a mobile computing device, a tablet computing device, aportable television, a portable video game console, or any other devicecapable of communicating with the RAN 104. The UEs 102 can communicatewith the RAN 104 by way of one or more eNodeBs (“eNBs”), such as an eNB106. Although only a single eNB 106 is shown, the RAN 104 can supportmultiple eNBs configured the same as or similar to the eNB 106.

The RAN 104 can include one or more service areas (“cells”) having thesame or different cell sizes, which may be represented by differentcell-types. As used herein, a “cell” refers to a geographical area thatis served by one or more base stations operating within an accessnetwork. The cells within the RAN 104 can include the same or differentcell sizes, which may be represented by different cell-types. Acell-type can be associated with certain dimensional characteristicsthat define the effective radio range of a cell. Cell-types can include,but are not limited to, a macro cell-type, a metro cell-type, a femtocell-type, a pico cell-type, a micro cell-type, wireless local areanetwork (“WLAN”) cell-type, and a white space network cell-type. Forease of explanation, a “small cell” cell-type is utilized herein tocollectively refer to a group of cell-types that includes femtocell-type, pico cell-type, and micro cell-type, in general contrast to amacro cell-type, which offers a larger coverage area. Other cell-types,including proprietary cell-types and temporary cell-types are alsocontemplated. Although in the illustrated example, the UEs 102 are shownas being in communication with one RAN (i.e., the RAN 104), the UEs 102may be in communication with any number of access networks, includingnetworks that incorporate collocated wireless wide area network (“WWAN”)WI-FI and cellular technologies, and as such, the UEs 102 can bedual-mode devices.

The RAN 104 can operate in accordance with one or more radio accesstechnologies (“RAT”) that utilize mobile telecommunications standardsincluding, but not limited to, Global System for Mobile communications(“GSM”), Code Division Multiple Access (“CDMA”) ONE, CDMA2000, UniversalMobile Telecommunications System (“UMTS”), LTE, WorldwideInteroperability for Microwave Access (“WiMAX”), other current 3GPPcellular technologies, other future 3GPP cellular technologies,combinations thereof, and/or the like. The RAN 104 can utilize variouschannel access methods (which may or may not be used by theaforementioned standards), including, but not limited to, Time DivisionMultiple Access (“TDMA”), Frequency Division Multiple Access (“FDMA”),CDMA, wideband CDMA (“W-CDMA”), Orthogonal Frequency DivisionMultiplexing (“OFDM”), Single-Carrier FDMA (“SC-FDMA”), Space DivisionMultiple Access (“SDMA”), and the like to provide a radio/air interfaceto the UEs 102. Data communications can be provided in part by the RAN104 using General Packet Radio Service (“GPRS”), Enhanced Data rates forGlobal Evolution (“EDGE”), the High-Speed Packet Access (“HSPA”)protocol family including High-Speed Downlink Packet Access (“HSDPA”),Enhanced Uplink (“EUL”) or otherwise termed High-Speed Uplink PacketAccess (“HSUPA”), Evolved HSPA (“HSPA+”), LTE, and/or various othercurrent and future wireless data access technologies. Moreover, the RAN104 may be a GSM RAN (“GRAN”), a GSM EDGE RAN (“GERAN”), a UMTSTerrestrial Radio Access Network (“UTRAN”), an evolved U-TRAN(“E-UTRAN”), any combination thereof, and/or the like. The concepts andtechnologies disclosed herein will be described in context of the RAN104 operating in accordance with LTE, although those skilled in the artwill appreciate the applicability of the concepts and technologiesdisclosed herein to other cellular technologies, including, inparticular, those captured within future generation 3GPP standards.Moreover, in some embodiments, the RAN 104 is or includes one or morevirtual RANs (“vRANs”).

As used herein, a “base station” refers to a radio receiver and/ortransmitter (collectively, transceiver) that is/are configured toprovide a radio/air interface over which one or more of the UEs 102 canconnect to a network. Accordingly, a base station is intended toencompass one or more base transceiver stations (“BTSs”), one or moreNBs, one or more eNBs (e.g., the eNB 106), one or more home eNBs, one ormore wireless access points (“APs”), one or more multi-standard metrocell (“MSMC”) nodes, and/or other networking nodes or combinationsthereof that are capable of providing a radio/air interface regardlessof the technologies utilized to do so. A base station can be incommunication with one or more antennas (not shown), each of which maybe configured in accordance with any antenna design specifications toprovide a physical interface for receiving and transmitting radio wavesto and from one or more devices, such as the UEs 102.

The RAN 104 is shown as being in communication with an evolved packetcore (“EPC”) network 108. The EPC network 108 provides core networkfunctions in accordance with Third Generation Partnership Project(“3GPP”) standards specifications. Accordingly, the EPC network 108 caninclude a plurality of EPC network elements (“EPC network elements”)110, such as, for example, one or more mobility management entity(“MMEs”), one or more home subscriber servers (“HSSs”), one or moreserving gateways (“SGWs”), one or more packet data network (“PDN”)gateways (“PGWs”), one or more combination SGW/PGWs, one or more policyand charging rules functions (“PCRFs”), some combination thereof, and/orthe like.

The EPC network elements 110 can be provided, at least in part, byphysical network functions (“PNFs”) having hardware and softwarecomponents that facilitate voice and/or data communications with the UEs102 and/or other devices (not shown). The EPC network elements 110 canadditionally or alternatively be provided, at least in part, by virtualnetwork functions (“VNFs”). For example, the EPC network elements 110can be realized as VNFs that utilize a unified commercial-off-the-shelf(“COTS”) hardware and flexible resources shared model with theapplication software for the respective EPC network elements running onone or more virtual machines (“VMs”). An example network functionsvirtualization platform (“NFVP”) architecture that might be used toimplement at least a portion of the EPC network elements 110 as VNFs isdescribed herein below with reference to FIG. 8.

An MME operating within the EPC network 108 can be configured inaccordance with 3GPP standards specifications. An MME, in general, canperform operations to control signaling traffic related to mobility andsecurity for access to the RAN 104.

An SGW can be configured in accordance with 3GPP standardsspecifications. An SGW provides a point of interconnect between theradio-side (e.g., the RAN 104) and the EPC network 108. An SGW servesthe UEs 102 by routing incoming and outgoing IP packets. A PGW can beconfigured in accordance with 3GPP standards specifications. A PGWinterconnects the EPC network 108 and one or more external IP networks,such as, in the illustrated embodiment, one or more other networks 112.The other network(s) 112 can include other public land mobile networks(“PLMNs”), PDNs, circuit-switched networks, operator IP service networks(e.g., IP multimedia subsystem), combinations thereof, and/or the like.

A PGW routes IP packets to and from the other network(s) 112. A PGW alsoperforms operations such as IP address/IP prefix allocation, policycontrol, and charging. In some implementations, a PGW and an SGW aredeployed as independent network components, and in other implementationsas a combined network component offering functionality of both a PGW andan SGW.

An HSS can be configured in accordance with 3GPP standardsspecifications. An HSS is a database that contains user-relatedinformation for users of devices, such as the UEs 102. An HSS canprovide support functions to one or more MMES for mobility management,call and session setup, user authentication, and access authorization.

A PCRF can be configured in accordance with 3GPP standardsspecifications. A PCRF can determine policy rules, detect service dataflows, enforce policies, and perform flow-based charging.

The illustrated EPC network 108 additionally includes a plurality ofDIAMETER resources (“DIAMETER resources”) 114. The DIAMETER resources114 can include a plurality of DIAMETER nodes that implement theDIAMETER protocol. The DIAMETER protocol is an AAA protocol that workson the application layer of the OSI model. DIAMETER is a message-basedprotocol, whereby end points exchange messages and receive positive ornegative acknowledgements. DIAMETER protocol is well-documented intechnical specifications such as those available from the IETF,particularly RFC 6733 and related documents.

Referring briefly to FIG. 2, a block diagram illustrating anillustrative DIAMETER protocol stack 200 capable of being utilized toimplement aspects of the embodiments presented herein will be described.The DIAMETER protocol stack 200 includes DIAMETER applications 202,DIAMETER interfaces 204, DIAMETER base protocol 206,transfer/transmission control protocol (“TCP”) 208, and Internetprotocol (“IP”) 210.

The IP 210 is a low-level network protocol that is used for theaddressing and routing of packets through data networks. The IP 210utilizes routing information and does not utilize data confirmationrules. To ensure reliable data transfer using the IP 210, higher levelprotocols such as the TCP 208 are used. The IP 210 can be implemented inaccordance with the specification set forth in RFC-791 and relateddocuments. The IP 210 defines the packet datagrams that hold packetdelivery addressing, type of service specification, dividing andre-assembly of long data files and data security.

The TCP 208 is a transport layer protocol that coordinates thetransmission, reception, and retransmission of packets in a data networkto ensure reliable (i.e., confirmed) communication. The TCP 208coordinates the division of data information into packets, adds sequenceand flow control information to the packets, and coordinates theconfirmation and retransmission of packets that are lost during acommunication session. The TCP 208 utilizes the IP 210 as the networklayer protocol. The TCP 208 can be implemented in accordance with thespecification set forth in RFC-793 and related documents.

The DIAMETER base protocol 206 provides an AAA framework forapplications such as network IP mobility in both local and roamingscenarios. The DIAMETER base protocol 206 specifies how DIAMETER nodesare to exchange messages and to deliver attribute-value pairs (“AVPs”).The DIAMETER base protocol 206 specifies the procedure for capabilitiesnegotiation and error notification. The DIAMETER base protocol 206provides basics services that can be called via an applicationprogramming interface (“API”) by the DIAMETER applications 202. TheDIAMETER base protocol 206 can be implemented in accordance with thespecification set forth in RRC-6733 and related documents.

The DIAMETER interfaces 204 provide connections between DIAMETER nodesto enable functions related to AAA for services. The DIAMETER interfaces204 can include, by way of example, one or more of the followinginterfaces: Sha, S6b, S6c, S6d, S9, S13, S13, SLg, Gx, Gy, Gz, Gi, SGi,Sp, Rx, Rx+, and Wm. The DIAMETER interfaces 204 can include otherinterfaces not explicitly mentioned herein, and can include, forexample, interfaces later defined. It should be understood that not allinterfaces will be utilized in a given DIAMETER session. Some of themore commonly used DIAMETER interfaces will now be described in greaterdetail below.

The interface Sha lies between an HSS and an MME for authentication andauthorization. The interface Sha can transport subscriber-related data,location information, and authentication/authorization informationbetween the HSS and the MME.

The interface SLg lies between an MME and a gateway mobility locationcenter (“GMLC”). The interface SLg enables transfer of locationinformation from the GMLC to the MME.

The interface Gx lies between a PCRF and a policy control andenforcement function (“PCEF”). The interface Gx enables transfer of QoSpolicy and charging rules from the PCRF to the PCEF.

The interface Rx lies between an application function and a PCRF. Theinterface Rx enables QoS functions.

The DIAMETER applications 202 extend the functionality provided by theDIAMETER base protocol 206 by adding new commands and/or attributes andcalling the DIAMETER base protocol 206 API. The DIAMETER applications202 can be proprietary applications or standardized applications, suchas those found in RFC-4004, RFC-4005, RFC-4006, RFC-4072, RFC-4740, andRFC-5447, for example.

Returning to FIG. 1, the DIAMETER nodes of the DIAMETER resources 114can implement the DIAMETER protocol and can act as a DIAMETER agent, aDIAMETER client, or a DIAMETER server. A DIAMETER agent is a DIAMETERnode that provides relay, proxy, redirect, or translation functions.

A DIAMETER client is a DIAMETER node that supports DIAMETER clientapplications and the DIAMETER base protocol. DIAMETER clients can beimplemented, for example, at the network edge and can provide accesscontrol services for the network. Some examples of DIAMETER clientsinclude network access servers and mobile IP foreign agents.

A DIAMETER server is a DIAMETER node that handles authentication,authorization, and accounting requests for a particular realm. ADIAMETER server supports DIAMETER server applications and the DIAMETERbase protocol.

A DIAMETER relay agent relays forward requests and responses based onrouting-related AVPs and routing table entries. Since DIAMETER relayagents do not make policy decisions, these agents do not examine oralter non-routing AVPs. As a result, DIAMETER relay agents neveroriginate messages, do not need to understand the semantics of messagesor non-routing AVPs, and are capable of handling any DIAMETERapplication or message type. Moreover, since DIAMETER relay agents makedecisions based on information in routing AVPs and forwarding tables,these agents do not maintain state on NAS resource usage or sessions inprogress.

A DIAMETER proxy agent can perform operations similar to a DIAMETERrelay agent. In addition, DIAMETER proxy agents can make policydecisions relating to resource usage and provisioning. DIAMETER proxyagents can make these decisions by tracking the state of NAS devices.While DIAMETER proxy agents do not respond to DIAMETER client requestsprior to receiving a response from a DIAMETER server, DIAMETER proxyagents can issue reject messages in cases where policies are violated.As such, DIAMETER proxy agents are designed to understand the semanticsof passing messages, and might not support all DIAMETER applications.

A DIAMETER redirect agent does not forward requests and responsesbetween DIAMETER clients and DIAMETER servers, and instead redirectsDIAMETER client and DIAMETER servers to allow direct communicationsbetween client/server. DIAMETER redirect agents do not alter AVPsexchanged between DIAMETER clients and DIAMETER servers. DIAMETERredirect agents also do not originate messages and are capable ofhandling any message type. Like DIAMETER relay agents, DIAMETER redirectagents do not maintain state on NAS resource usage or sessions inprogress.

A DIAMETER translation agent is a stateful DIAMETER node that performsprotocol translation between AAA protocols. For example, a DIAMETERtranslation agent can perform protocol translation between DIAMETER andanother AAA protocol, such as RADIUS.

A DIAMETER peer is a DIAMETER node to which another DIAMETER node has adirect transport connection. The illustrated EPC network 108additionally includes a plurality of transport resources 116 capable ofsupporting transport connections between DIAMETER peers. The transportconnection operates according to transfer control protocol (“TCP”) orstream control transfer protocol (“SCTP”). Two DIAMETER nodes that sharea direct TCP or SCTP transport connection are referred to herein asDIAMETER peers.

The DIAMETER resources 114 can additionally include one or more DIAMETERrouting agents (“DRAs”). A DRA is a specialized DIAMETER relay agentdesigned in accordance with 3GPP standards specifications. A DRA is afunctional element in a 3G or 4G (e.g., LTE) network that providesreal-time routing capabilities to ensure that messages are routed amongthe correct elements within a network. DRAs were introduced by the 3GPPto address the increased DIAMETER signaling traffic and growingcomplexity of 4G LTE networks. A DRA can provide real-time routingcapabilities to ensure that DIAMETER signaling messages are routed tothe correct resources in the EPC network 108.

The DIAMETER resources 114 can additionally include one or more DIAMETERedge agents (“DEAs”). A DEA is a specialized DIAMETER client designed inaccordance with 3GPP standards specifications. A DEA provides a point ofcontact into and out of the EPC network 108 at the DIAMETER applicationlevel. A DEA provides secure communications to connect the EPC network108 to the other network(s) 112 to facilitate internetwork signalingoperations (e.g., roaming, charging, and billing), for example, betweenhome and visited PLMNs. A DEA can enable DIAMETER signaling traffic toflow core networks while also disguising the topology of the corenetworks to one another.

The DIAMETER resources 114 can be virtualized resources that utilize aunified COTS hardware and flexible resources shared model with theapplication software for the respective DIAMETER resources running onone or more VMs. An example NFVP architecture that might be used toimplement at least a portion of the DIAMETER resources 114 is describedherein below with reference to FIG. 8.

The EPC network 108 additionally includes a universal DIAMETERorchestrator 118. The universal DIAMETER orchestrator 118 can includeone or more processors that can execute instructions contained in adecision logic 120 to perform various functions. In particular, theuniversal DIAMETER orchestrator 118 can map all of the DIAMETERresources 114 available in the EPC network 108. The universal DIAMETERorchestrator 118 can dynamically select DIAMETER peer nodes for routingcontrol plane transactions on a particular signaling interface with agiven service. The universal DIAMETER orchestrator 118 can allocate thetransport resources 116 on-demand for intelligently routing DIAMETERapplication signaling traffic between the two selected DIAMETER peernodes through a DIAMETER agent within the EPC network 108. The universalDIAMETER orchestrator 118 can enforce rules 122 on-demand to overridetraditional DRA-based routing with direct DIAMETER peering to acceleratecompletion of certain transactions for a given prioritized service typethat requires higher QoS or to maintain accordance with a service levelagreement. The universal DIAMETER orchestrator 118 can consider thesession/transaction based application signaling traffic priority basedon the source and destination peer nodes that need to communicate toperform a specific transaction and a pair of transactions required for agiven service. The universal DIAMETER orchestrator 118 can analyze theDIAMETER protocol stack 200 (described above with reference to FIG. 2)to ensure that the transport resources 116 are optimally allocated tomeet the transaction exchange on a service level basis. The universalDIAMETER orchestrator 118 can create a mapping of critical transactioncompletion times and hysteresis of the DIAMETER resources 114 used tomeet such metrics for predictive allocation. The universal DIAMETERorchestrator 118 can monitor signaling traffic exchange, create astructured representation of DIAMETER application data, and can presentthis data in a standardized format, such as, for example, JSON, foreasier integration with network analytics engines. The universalDIAMETER orchestrator 118 can distribute user data transfer capabilityover DIAMETER applications across multiple DIAMETER peer nodes so as tosaturate a given DIAMETER peer node pair. The universal DIAMETERorchestrator 118 can perform real-time configuration management of thetransport resources 116 across regional pools with multi-vendor systems.The universal DIAMETER orchestrator 118 can perform real-timeperformance management of transport resources 116 across regional poolswith multi-vendor systems. The universal DIAMETER orchestrator 118 canperform real-time performance management of DIAMETER signaling exchangesover the allocated transport resources 116 per transaction per servicetype across regional pools with multi-vendor systems. The universalDIAMETER orchestrator 118 can provide a dashboard that outputsservice-based analytics in a closed-loop manner to isolate faults and toreroute traffic to maintain transaction continuity.

The illustrated operating environment 100 also illustrates the UEs 102being capable of utilizing one or more services 124A-124N (referred toherein collectively as services 124, or in the singular form as service124). The services 124 can include, for example, video, social network,social media, Voice over Long-Term Evolution (“VoLTE”), e-commerce,multimedia, and messaging. The UE 102 can execute one or more serviceapplications 126A-126N (referred to herein collectively as serviceapplications 126, or in the singular form as service application 126) toutilize the services 124. A service application 126 can include, in oneembodiment, a web browser application that allows users to access webportals, link pages, web sites, and/or other information available onthe World Wide Web. In some other embodiments, the service application126 can include a native application that is installed on the UE 102 andallows the UE 102 to utilize one or more services 124. The serviceapplications 126A-126N can generate service requests 128A-128N,respectively, and can send the service requests 128A-128N (referred toherein collectively as service requests 128, or in the singular form asservice request 128) to the EPC network 108 via the RAN 104. Theuniversal DIAMETER orchestrator 118 can inspect the service requests128A-128N, and utilize the decision logic 120 and rules 122 to determinehow to set up the DIAMETER resources 114 and the transport resources 116to meet signaling requirements of the services identified in the servicerequests 128A-128N.

Turning now to FIG. 3, a block diagram illustrating a traditionalconfiguration 300 for DIAMETER orchestration in accordance with priorimplementations will be described. In the illustrated configuration 300,a source domain 302 and a destination domain 304 in which at least aportion of the EPC network elements 110 from FIG. 1 are illustrated. TheEPC network elements 110 shown in FIG. 3 are implemented as VNFs,including vMMEs 306A-306B, a vPCEF 308, a vCSCF 310, a vHSS 312, a vGMLC314, and vPCRFs 316A-316B.

The vMME₁ 306A is shown as being in communication with the vHSS 312 viaan S6a DIAMETER interface 318 for handling DIAMETER signaling trafficbetween these VNFs. The vMME₂ 306B is shown as being in communicationwith the vGMLC 314 via an SLg DIAMETER interface 320 for handlingDIAMETER signaling traffic between these VNFs. The vPCEF 308 is shown asbeing in communication with the vPCRF₁ 316A via a Gx DIAMETER interface322 for handling DIAMETER signaling traffic between these VNFs. ThevCSCF 310 is shown as being in communication with the vPCRF₂ 316B via anRx DIAMETER interface 324 for handling DIAMETER signaling trafficbetween these VNFs.

The illustrated configuration 300 also includes a dedicated DRA for eachof the aforementioned interfaces. In particular, DIAMETER signalingtraffic over the S6a DIAMETER interface 318 can be routed by a DRA-S6a326; DIAMETER signaling traffic over the SLg DIAMETER interface 320 canbe routed by a DRA-SLg 328; DIAMETER signaling traffic over the GxDIAMETER interface 322 can be routed by a DRA-Gx 330; and DIAMETERsignaling traffic over the Rx DIAMETER interface 324 can be routed by aDRA-Rx 332. Each of the dedicated DRAs 326-332 can send individualDIAMETER signaling traffic requests in an ad-hoc fashion to anorchestration engine 334. The orchestration engine 334 determinesoverall resources assignment in response to the requests and respondsaccordingly with the allocations. By actively monitoring these resourceallocations and/or de-allocations, the orchestration engine 334maintains a current view of the overall resources required to supporttransactional exchanges between any two peer nodes in the EPC network108 to support a given service.

Turning now to FIG. 4, a block diagram illustrating a configuration 400for DIAMETER orchestration will be described, according to anillustrative embodiment. In the illustrated configuration 400, thesource domain 302 and the destination domain 304 from FIG. 3 areduplicated. The EPC network elements 110 shown in FIG. 4 are implementedas VNFs, including the vMMEs 306A-306B, the vPCEF 308, the vCSCF 310,the vHSS 312, the vGMLC 314, and the vPCRFs 316A-316B.

The vMME₁ 306A is shown as being in communication with the vHSS 312 viathe Sha DIAMETER interface 318 for handling DIAMETER signaling trafficbetween these VNFs. The vMME₂ 306B is shown as being in communicationwith the vGMLC 314 via the SLg DIAMETER interface 320 for handlingDIAMETER signaling traffic between these VNFs. The vPCEF 308 is shown asbeing in communication with the vPCRF₁ 316A via the Gx DIAMETERinterface 322 for handling DIAMETER signaling traffic between theseVNFs. The vCSCF 310 is shown as being in communication with the vPCRF₂316B via the Rx DIAMETER interface 324 for handling DIAMETER signalingtraffic between these VNFs.

The illustrated configuration 400 also includes a signalingorchestration domain 402 in which the universal DIAMETER orchestrator118 and the DIAMETER resources 114 described above with reference toFIG. 1 reside. The universal DIAMETER orchestrator 118 can receive aservice request (e.g., any of the service requests 128A-128N shown inFIG. 1), identify the service 124 requested, identify the DIAMETER peernodes operating in the source domain 302 and the destination domain 304required to support DIAMETER signaling traffic associated with providingthe service 124 identified in the service request (e.g., the respectiveone or more of the service requests 128A-128N), and can allocate atleast a portion of the DIAMETER resources 114 needed to support theDIAMETER signaling traffic.

For example, if a non-IP LTE capable M2M type communication device usedfor IoT service delivery has been in sleep mode for a long time topreserve battery/power and needs to wake up to send/receive data from anexternal IoT server, the device can setup a non-IP PDN connection on anew 3GPP-defined T6a DIAMETER interface between an MME and a servicecapability exposure function (“SCEF”). The universal DIAMETERorchestrator 118 can dynamically allocate the resources for such non-IPPDN connections on-demand over the T6a DIAMETER interface to ensure thattransactions are completed successfully. In a similar manner, for largescale traffic handling from IoT devices serving across multiple industryverticals, the universal DIAMETER orchestrator 118 can dynamicallyallocate/de-allocate resources to establish/teardown PDN connectionson-demand and to ensure that resources across the peers are maintainedat healthy levels to avoid any potential failure scenarios that couldotherwise result in network outage and/or malfunctioning in stormy ordisaster type situations.

Turning now to FIG. 5, aspects of a method 500 for DIAMETERorchestration will be described, according to an illustrativeembodiment. It should be understood that the operations of the methodsdisclosed herein are not necessarily presented in any particular orderand that performance of some or all of the operations in an alternativeorder(s) is possible and is contemplated. The operations have beenpresented in the demonstrated order for ease of description andillustration. Operations may be added, omitted, and/or performedsimultaneously, without departing from the scope of the concepts andtechnologies disclosed herein.

It also should be understood that the methods disclosed herein can beended at any time and need not be performed in its entirety. Some or alloperations of the methods, and/or substantially equivalent operations,can be performed by execution of computer-readable instructions includedon a computer storage media, as defined herein. The term“computer-readable instructions,” and variants thereof, as used herein,is used expansively to include routines, applications, applicationmodules, program modules, programs, components, data structures,algorithms, and the like. Computer-readable instructions can beimplemented on various system configurations including single-processoror multiprocessor systems, minicomputers, mainframe computers, personalcomputers, hand-held computing devices, microprocessor-based,programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations describedherein are implemented (1) as a sequence of computer implemented acts orprogram modules running on a computing system and/or (2) asinterconnected machine logic circuits or circuit modules within thecomputing system. The implementation is a matter of choice dependent onthe performance and other requirements of the computing system.Accordingly, the logical operations described herein are referred tovariously as states, operations, structural devices, acts, or modules.These states, operations, structural devices, acts, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof. As used herein, the phrase “cause aprocessor to perform operations” and variants thereof is used to referto causing one or more processors disclosed herein to performoperations.

For purposes of illustrating and describing some of the concepts of thepresent disclosure, the method 500 is described as being performed, atleast in part, by the universal DIAMETER orchestrator 118 via executionof one or more software modules, such as the decision logic 120. Itshould be understood that additional and/or alternative devices and/ornetwork nodes can provide the functionality described herein viaexecution of one or more modules, applications, and/or other software.Thus, the illustrated embodiments are illustrative, and should not beviewed as being limiting in any way.

The method 500 will be described with reference to FIG. 5 and furtherreference to FIGS. 1 and 4. The method 500 begins at operation 502,where the universal DIAMETER orchestrator 118 receives the servicerequest 128 from the UE 102. From operation 502, the method 500 proceedsto operation 504, where the universal DIAMETER orchestrator 118 analyzesthe service request 128 to identify the service 124 requested. Fromoperation 504, the method 500 proceeds to operation 506, where theuniversal DIAMETER orchestrator 118 determines one or more DIAMETERapplications to be utilized to meet DIAMETER signaling requirements ofthe service 124.

From operation 506, the method 500 proceeds to operation 508, where theuniversal DIAMETER orchestrator 118 determines the DIAMETER peer nodesto be utilized to provide the service 124. From operation 508, themethod 500 proceeds to operation 510, where the universal DIAMETERorchestrator 118 allocates at least a portion of the transport resources116 over which to create one or more transport connections betweenDIAMETER peer nodes.

From operation 510, the method 500 proceeds to operation 512, where theuniversal DIAMETER orchestrator 118 allocates at least a portion of theDIAMETER resources 114 to provision one or more DIAMETER signalinginterfaces between the DIAMETER peer nodes. From operation 512, themethod 500 proceeds to operation 514, where the method 500 ends.

Turning now to FIG. 6, an illustrative mobile device 600 and componentsthereof will be described. In some embodiments, one or more of the UEs102 (shown in FIG. 1) can be configured like the mobile device 600.While connections are not shown between the various componentsillustrated in FIG. 6, it should be understood that some, none, or allof the components illustrated in FIG. 6 can be configured to interactwith one other to carry out various device functions. In someembodiments, the components are arranged so as to communicate via one ormore busses (not shown). Thus, it should be understood that FIG. 6 andthe following description are intended to provide a generalunderstanding of a suitable environment in which various aspects ofembodiments can be implemented, and should not be construed as beinglimiting in any way.

As illustrated in FIG. 6, the mobile device 600 can include a display602 for displaying data. According to various embodiments, the display602 can be configured to display various graphical user interface(“GUI”) elements, text, images, video, virtual keypads and/or keyboards,messaging data, notification messages, metadata, internet content,device status, time, date, calendar data, device preferences, map andlocation data, combinations thereof, and/or the like. The mobile device600 also can include a processor 604 and a memory or other data storagedevice (“memory”) 606. The processor 604 can be configured to processdata and/or can execute computer-executable instructions stored in thememory 606. The computer-executable instructions executed by theprocessor 604 can include, for example, an operating system 608, one ormore applications 610, other computer-executable instructions stored ina memory 606, or the like. In some embodiments, the applications 610also can include a user interface (“UI”) application (not illustrated inFIG. 6).

The UI application can interface with the operating system 608 tofacilitate user interaction with functionality and/or data stored at themobile device 600 and/or stored elsewhere. In some embodiments, theoperating system 608 can include a member of the SYMBIAN OS family ofoperating systems from SYMBIAN LIMITED, a member of the WINDOWS MOBILEOS and/or WINDOWS PHONE OS families of operating systems from MICROSOFTCORPORATION, a member of the PALM WEBOS family of operating systems fromHEWLETT PACKARD CORPORATION, a member of the BLACKBERRY OS family ofoperating systems from RESEARCH IN MOTION LIMITED, a member of the IOSfamily of operating systems from APPLE INC., a member of the ANDROID OSfamily of operating systems from GOOGLE INC., and/or other operatingsystems. These operating systems are merely illustrative of somecontemplated operating systems that may be used in accordance withvarious embodiments of the concepts and technologies described hereinand therefore should not be construed as being limiting in any way.

The UI application can be executed by the processor 604 to aid a user inentering content, viewing account information, answering/initiatingcalls, entering/deleting data, entering and setting user IDs andpasswords for device access, configuring settings, manipulating addressbook content and/or settings, multimode interaction, interacting withother applications 610, and otherwise facilitating user interaction withthe operating system 608, the applications 610, and/or other types orinstances of data 612 that can be stored at the mobile device 600. Theother applications 610 can include the service application 126. The data612 can include, for example, one or more identifiers, and/or otherapplications or program modules. According to various embodiments, thedata 612 can include, for example, presence applications, visual voicemail applications, messaging applications, text-to-speech andspeech-to-text applications, add-ons, plug-ins, email applications,music applications, video applications, camera applications,location-based service applications, power conservation applications,game applications, productivity applications, entertainmentapplications, enterprise applications, combinations thereof, and thelike. The applications 610, the data 612, and/or portions thereof can bestored in the memory 606 and/or in a firmware 614, and can be executedby the processor 604. The firmware 614 also can store code for executionduring device power up and power down operations. It can be appreciatedthat the firmware 614 can be stored in a volatile or non-volatile datastorage device including, but not limited to, the memory 606 and/or aportion thereof.

The mobile device 600 also can include an input/output (“I/O”) interface616. The I/O interface 616 can be configured to support the input/outputof data such as location information, user information, organizationinformation, presence status information, user IDs, passwords, andapplication initiation (start-up) requests. In some embodiments, the I/Ointerface 616 can include a hardwire connection such as USB port, amini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394(“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ45)port, an RJ10 port, a proprietary port, combinations thereof, or thelike. In some embodiments, the mobile device 600 can be configured tosynchronize with another device to transfer content to and/or from themobile device 600. In some embodiments, the mobile device 600 can beconfigured to receive updates to one or more of the applications 610 viathe I/O interface 616, though this is not necessarily the case. In someembodiments, the I/O interface 616 accepts I/O devices such askeyboards, keypads, mice, interface tethers, printers, plotters,external storage, touch/multi-touch screens, touch pads, trackballs,joysticks, microphones, remote control devices, displays, projectors,medical equipment (e.g., stethoscopes, heart monitors, and other healthmetric monitors), modems, routers, external power sources, dockingstations, combinations thereof, and the like. It should be appreciatedthat the I/O interface 616 may be used for communications between themobile device 600 and a network device or local device.

The mobile device 600 also can include a communications component 618.The communications component 618 can be configured to interface with theprocessor 604 to facilitate wired and/or wireless communications withone or more networks such as one or more IP access networks and/or oneor more circuit access networks. In some embodiments, other networksinclude networks that utilize non-cellular wireless technologies such asWI-FI or WIMAX. In some embodiments, the communications component 618includes a multimode communications subsystem for facilitatingcommunications via the cellular network and one or more other networks.

The communications component 618, in some embodiments, includes one ormore transceivers. The one or more transceivers, if included, can beconfigured to communicate over the same and/or different wirelesstechnology standards with respect to one another. For example, in someembodiments one or more of the transceivers of the communicationscomponent 618 may be configured to communicate using GSM, CDMA ONE,CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, and greatergeneration technology standards. Moreover, the communications component618 may facilitate communications over various channel access methods(which may or may not be used by the aforementioned standards)including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and thelike.

In addition, the communications component 618 may facilitate datacommunications using GPRS, EDGE, the HSPA protocol family includingHSDPA, EUL or otherwise termed HSUPA, HSPA+, and various other currentand future wireless data access standards. In the illustratedembodiment, the communications component 618 can include a firsttransceiver (“TxRx”) 620A that can operate in a first communicationsmode (e.g., GSM). The communications component 618 also can include anN^(th) transceiver (“TxRx”) 620N that can operate in a secondcommunications mode relative to the first transceiver 620A (e.g., UMTS).While two transceivers 620A-620N (hereinafter collectively and/orgenerically referred to as “transceivers 620”) are shown in FIG. 6, itshould be appreciated that less than two, two, and/or more than twotransceivers 620 can be included in the communications component 618.

The communications component 618 also can include an alternativetransceiver (“Alt TxRx”) 622 for supporting other types and/or standardsof communications. According to various contemplated embodiments, thealternative transceiver 622 can communicate using various communicationstechnologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared,infrared data association (“IRDA”), near-field communications (“NFC”),ZIGBEE, other radio frequency (“RF”) technologies, combinations thereof,and the like.

In some embodiments, the communications component 618 also canfacilitate reception from terrestrial radio networks, digital satelliteradio networks, internet-based radio service networks, combinationsthereof, and the like. The communications component 618 can process datafrom a network such as the Internet, an intranet, a broadband network, aWI-FI hotspot, an Internet service provider (“ISP”), a digitalsubscriber line (“DSL”) provider, a broadband provider, combinationsthereof, or the like.

The mobile device 600 also can include one or more sensors 624. Thesensors 624 can include temperature sensors, light sensors, air qualitysensors, movement sensors, orientation sensors, noise sensors, proximitysensors, or the like. As such, it should be understood that the sensors624 can include, but are not limited to, accelerometers, magnetometers,gyroscopes, infrared sensors, noise sensors, microphones, combinationsthereof, or the like. Additionally, audio capabilities for the mobiledevice 600 may be provided by an audio I/O component 626. The audio I/Ocomponent 626 of the mobile device 600 can include one or more speakersfor the output of audio signals, one or more microphones for thecollection and/or input of audio signals, and/or other audio inputand/or output devices.

The illustrated mobile device 600 also can include a subscriber identitymodule (“SIM”) system 628. The SIM system 628 can include a universalSIM (“USIM”), a universal integrated circuit card (“UICC”) and/or otheridentity devices. The SIM system 628 can include and/or can be connectedto or inserted into an interface such as a slot interface 630. In someembodiments, the slot interface 630 can be configured to acceptinsertion of other identity cards or modules for accessing various typesof networks. Additionally, or alternatively, the slot interface 630 canbe configured to accept multiple subscriber identity cards. Becauseother devices and/or modules for identifying users and/or the mobiledevice 600 are contemplated, it should be understood that theseembodiments are illustrative, and should not be construed as beinglimiting in any way.

The mobile device 600 also can include an image capture and processingsystem 632 (“image system”). The image system 632 can be configured tocapture or otherwise obtain photos, videos, and/or other visualinformation. As such, the image system 632 can include cameras, lenses,charge-coupled devices (“CCDs”), combinations thereof, or the like. Themobile device 600 may also include a video system 634. The video system634 can be configured to capture, process, record, modify, and/or storevideo content. Photos and videos obtained using the image system 632 andthe video system 634, respectively, may be added as message content toan MMS message, email message, and sent to another mobile device. Thevideo and/or photo content also can be shared with other devices viavarious types of data transfers via wired and/or wireless communicationdevices as described herein.

The mobile device 600 also can include one or more location components636. The location components 636 can be configured to send and/orreceive signals to determine a geographic location of the mobile device600. According to various embodiments, the location components 636 cansend and/or receive signals from global positioning system (“GPS”)devices, assisted GPS (“A-GPS”) devices, WI-FI/WIMAX and/or cellularnetwork triangulation data, combinations thereof, and the like. Thelocation component 636 also can be configured to communicate with thecommunications component 618 to retrieve triangulation data fordetermining a location of the mobile device 600. In some embodiments,the location component 636 can interface with cellular network nodes,telephone lines, satellites, location transmitters and/or beacons,wireless network transmitters and receivers, combinations thereof, andthe like. In some embodiments, the location component 636 can includeand/or can communicate with one or more of the sensors 624 such as acompass, an accelerometer, and/or a gyroscope to determine theorientation of the mobile device 600. Using the location component 636,the mobile device 600 can generate and/or receive data to identify itsgeographic location, or to transmit data used by other devices todetermine the location of the mobile device 600. The location component636 may include multiple components for determining the location and/ororientation of the mobile device 600.

The illustrated mobile device 600 also can include a power source 638.The power source 638 can include one or more batteries, power supplies,power cells, and/or other power subsystems including alternating current(“AC”) and/or direct current (“DC”) power devices. The power source 638also can interface with an external power system or charging equipmentvia a power I/O component 660. Because the mobile device 600 can includeadditional and/or alternative components, the above embodiment should beunderstood as being illustrative of one possible operating environmentfor various embodiments of the concepts and technologies describedherein. The described embodiment of the mobile device 600 isillustrative, and should not be construed as being limiting in any way.

Turning now to FIG. 7, a block diagram illustrating a computer system700 configured to provide the functionality in accordance with variousembodiments of the concepts and technologies disclosed herein isillustrated. The systems, devices, and other components disclosed hereincan utilize, at least in part, an architecture that is the same as or atleast similar to the architecture of the computer system 700, forexample, the UEs 102, the eNBs 106, the EPC network elements, 110,and/or the universal DIAMETER orchestrator 118. It should be understood,however, that modification to the architecture may be made to facilitatecertain interactions among elements described herein.

The computer system 700 includes a processing unit 702, a memory 704,one or more user interface devices 706, one or more input/output (“I/O”)devices 708, and one or more network devices 710, each of which isoperatively connected to a system bus 712. The system bus 712 enablesbi-directional communication between the processing unit 702, the memory704, the user interface devices 706, the I/O devices 708, and thenetwork devices 710.

The processing unit 702 may be a standard central processor thatperforms arithmetic and logical operations, a more specific purposeprogrammable logic controller (“PLC”), a programmable gate array, orother type of processor known to those skilled in the art and suitablefor controlling the operation of the server computer. Processing unitsare generally known, and therefore are not described in further detailherein.

The memory 704 communicates with the processing unit 702 via the systembus 712. In some embodiments, the memory 704 is operatively connected toa memory controller (not shown) that enables communication with theprocessing unit 702 via the system bus 712. The illustrated memory 704includes an operating system 714 and one or more program modules 716.The operating system 714 can include, but is not limited to, members ofthe WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operatingsystems from MICROSOFT CORPORATION, the LINUX family of operatingsystems, the SYMBIAN family of operating systems from SYMBIAN LIMITED,the BREW family of operating systems from QUALCOMM CORPORATION, the MACOS, OS X, and/or iOS families of operating systems from APPLECORPORATION, the FREEBSD family of operating systems, the SOLARIS familyof operating systems from ORACLE CORPORATION, other operating systems,and the like.

The program modules 716 may include various software and/or programmodules to perform the various operations described herein. The programmodules 716 and/or other programs can be embodied in computer-readablemedia containing instructions that, when executed by the processing unit702, perform various operations such as those described herein.According to embodiments, the program modules 716 may be embodied inhardware, software, firmware, or any combination thereof.

By way of example, and not limitation, computer-readable media mayinclude any available computer storage media or communication media thatcan be accessed by the computer system 700. Communication media includescomputer-readable instructions, data structures, program modules, orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any delivery media. The term “modulateddata signal” means a signal that has one or more of its characteristicschanged or set in a manner as to encode information in the signal. Byway of example, and not limitation, communication media includes wiredmedia such as a wired network or direct-wired connection, and wirelessmedia such as acoustic, RF, infrared and other wireless media.Combinations of the any of the above should also be included within thescope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules, or other data. Computer storage media includes, but isnot limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”),Electrically Erasable Programmable ROM (“EEPROM”), flash memory or othersolid state memory technology, CD-ROM, digital versatile disks (“DVD”),or other optical storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by the computer system 700. In the claims, the phrase “computerstorage medium” and variations thereof does not include waves or signalsper se and/or communication media.

The user interface devices 706 may include one or more devices withwhich a user accesses the computer system 700. The user interfacedevices 706 may include, but are not limited to, computers, servers,PDAs, cellular phones, or any suitable computing devices. The I/Odevices 708 enable a user to interface with the program modules 716. Inone embodiment, the I/O devices 708 are operatively connected to an I/Ocontroller (not shown) that enables communication with the processingunit 702 via the system bus 712. The I/O devices 708 may include one ormore input devices, such as, but not limited to, a keyboard, a mouse, oran electronic stylus. Further, the I/O devices 708 may include one ormore output devices, such as, but not limited to, a display screen or aprinter. In some embodiments, the I/O devices 708 can be used for manualcontrols for operations to exercise under certain emergency situations.

The network devices 710 enable the computer system 700 to communicatewith other networks or remote systems via a network 718. Examples of thenetwork devices 710 include, but are not limited to, a modem, a radiofrequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface,a bridge, a router, or a network card. The network 718 may be or mayinclude a wireless network such as, but not limited to, a Wireless LocalArea Network (“WLAN”), a Wireless Wide Area Network (“WWAN”), a WirelessPersonal Area Network (“WPAN”) such as provided via BLUETOOTHtechnology, a Wireless Metropolitan Area Network (“WMAN”) such as aWiMAX network or metropolitan cellular network. Alternatively, thenetwork 718 may be or may include a wired network such as, but notlimited to, a Wide Area Network (“WAN”), a wired Personal Area Network(“PAN”), or a wired Metropolitan Area Network (“MAN”).

Turning now to FIG. 8, a network functions virtualization platform(“NFVP”) 800 will be described, according to an exemplary embodiment.The architecture of the NFVP 800 can be used to implement VNFs of thePNFs disclosed herein. For example, the NFVP 800 can be utilized toimplement at least a portion of the EPC network elements 110. The NFVP800 additionally or alternatively can be utilized to implement theuniversal DIAMETER orchestrator 118. The NFVP 800 additionally oralternatively can be utilized to implement at least a portion of theDIAMETER resources 114 and/or the transport resources 116.

The NFVP 800 is a shared infrastructure that can support multipleservices and network applications. The illustrated NFVP 800 includes ahardware resource layer 802, a virtualization/control layer 804, and avirtual resource layer 806 that work together to perform operations aswill be described in detail herein.

The hardware resource layer 802 provides hardware resources, which, inthe illustrated embodiment, include one or more compute resources 808,one or more memory resources 810, and one or more other resources 812.The compute resource(s) 808 can include one or more hardware componentsthat perform computations to process data, and/or to executecomputer-executable instructions of one or more application programs,operating systems, and/or other software. The compute resources 808 caninclude one or more central processing units (“CPUs”) configured withone or more processing cores. The compute resources 808 can include oneor more graphics processing unit (“GPU”) configured to accelerateoperations performed by one or more CPUs, and/or to perform computationsto process data, and/or to execute computer-executable instructions ofone or more application programs, operating systems, and/or othersoftware that may or may not include instructions particular to graphicscomputations. In some embodiments, the compute resources 808 can includeone or more discrete GPUs. In some other embodiments, the computeresources 808 can include CPU and GPU components that are configured inaccordance with a co-processing CPU/GPU computing model, wherein thesequential part of an application executes on the CPU and thecomputationally-intensive part is accelerated by the GPU. The computeresources 808 can include one or more system-on-chip (“SoC”) componentsalong with one or more other components, including, for example, one ormore of the memory resources 810, and/or one or more of the otherresources 812. In some embodiments, the compute resources 808 can be orcan include one or more SNAPDRAGON SoCs, available from QUALCOMM of SanDiego, Calif.; one or more TEGRA SoCs, available from NVIDIA of SantaClara, Calif.; one or more HUMMINGBIRD SoCs, available from SAMSUNG ofSeoul, South Korea; one or more Open Multimedia Application Platform(“OMAP”) SoCs, available from TEXAS INSTRUMENTS of Dallas, Tex.; one ormore customized versions of any of the above SoCs; and/or one or moreproprietary SoCs. The compute resources 808 can be or can include one ormore hardware components architected in accordance with an ARMarchitecture, available for license from ARM HOLDINGS of Cambridge,United Kingdom. Alternatively, the compute resources 808 can be or caninclude one or more hardware components architected in accordance withan x86 architecture, such an architecture available from INTELCORPORATION of Mountain View, Calif., and others. Those skilled in theart will appreciate the implementation of the compute resources 808 canutilize various computation architectures, and as such, the computeresources 808 should not be construed as being limited to any particularcomputation architecture or combination of computation architectures,including those explicitly disclosed herein.

The memory resource(s) 810 can include one or more hardware componentsthat perform storage operations, including temporary or permanentstorage operations. In some embodiments, the memory resource(s) 810include volatile and/or non-volatile memory implemented in any method ortechnology for storage of information such as computer-readableinstructions, data structures, program modules, or other data disclosedherein. Computer storage media includes, but is not limited to, randomaccess memory (“RAM”), read-only memory (“ROM”), Erasable ProgrammableROM (“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flashmemory or other solid state memory technology, CD-ROM, digital versatiledisks (“DVD”), or other optical storage, magnetic cassettes, magnetictape, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to store data and which can be accessedby the compute resources 808.

The other resource(s) 812 can include any other hardware resources thatcan be utilized by the compute resources(s) 808 and/or the memoryresource(s) 810 to perform operations described herein. The otherresource(s) 812 can include one or more input and/or output processors(e.g., network interface controller or wireless radio), one or moremodems, one or more codec chipset, one or more pipeline processors, oneor more fast Fourier transform (“FFT”) processors, one or more digitalsignal processors (“DSPs”), one or more speech synthesizers, and/or thelike.

The hardware resources operating within the hardware resources layer 802can be virtualized by one or more virtual machine monitors (“VMMs”)814-814K (also known as “hypervisors”; hereinafter “VMMs 814”) operatingwithin the virtualization/control layer 804 to manage one or morevirtual resources that reside in the virtual resource layer 806. TheVMMs 814 can be or can include software, firmware, and/or hardware thatalone or in combination with other software, firmware, and/or hardware,manages one or more virtual resources operating within the virtualresource layer 806.

The virtual resources operating within the virtual resource layer 806can include abstractions of at least a portion of the compute resources808, the memory resources 810, the other resources 812, or anycombination thereof. These abstractions are referred to herein asvirtual machines (“VMs”). In the illustrated embodiment, the virtualresource layer 806 includes VMs 816-816N (hereinafter “VMs 816”). Eachof the VMs 816 can execute one or more applications.

Based on the foregoing, it should be appreciated that concepts andtechnologies directed to universal peer-to-peer signaling networkvirtualization and orchestration have been disclosed herein. Althoughthe subject matter presented herein has been described in languagespecific to computer structural features, methodological andtransformative acts, specific computing machinery, and computer-readablemedia, it is to be understood that the concepts and technologiesdisclosed herein are not necessarily limited to the specific features,acts, or media described herein. Rather, the specific features, acts andmediums are disclosed as example forms of implementing the concepts andtechnologies disclosed herein.

The subject matter described above is provided by way of illustrationonly and should not be construed as limiting. Various modifications andchanges may be made to the subject matter described herein withoutfollowing the example embodiments and applications illustrated anddescribed, and without departing from the true spirit and scope of theembodiments of the concepts and technologies disclosed herein.

1. A universal DIAMETER orchestrator comprising: a processor; and amemory that includes instructions that, when executed by the processor,cause the universal DIAMETER orchestrator to perform operationscomprising: identifying a service of an evolved packet core network tobe provided to a user equipment device, selecting DIAMETER peer nodesoperating in a source domain and a destination domain of the evolvedpacket core network to support DIAMETER signaling traffic associatedwith the service, wherein the DIAMETER peer nodes share a directtransport connection between the source domain and the destinationdomain of the evolved packet core network, and allocating DIAMETERresources within the evolved packet core network to support the DIAMETERsignaling traffic between the DIAMETER peer nodes over the directtransport connection.
 2. The universal DIAMETER orchestrator of claim 1,wherein the operations further comprise receiving, from a serviceapplication, a service request specifying the service to be provided tothe user equipment device.
 3. The universal DIAMETER orchestrator ofclaim 1, wherein the DIAMETER signaling traffic between the DIAMETERpeer nodes is routed through a DIAMETER agent of the DIAMETER resourceswithin the evolved packet core network.
 4. The universal DIAMETERorchestrator of claim 1, wherein the operations further compriseallocating at least a portion of transport resources to create thedirect transport connection between the DIAMETER peer nodes.
 5. Theuniversal DIAMETER orchestrator of claim 1, wherein the operationsfurther comprise: determining a DIAMETER application to be utilized tomeet a DIAMETER signaling requirement of the service, creating astructured representation of DIAMETER application data associated withthe DIAMETER application, and reporting the structured representation tointegrate with a network analytics engine.
 6. The universal DIAMETERorchestrator of claim 5, wherein the operations further compriseanalyzing a structured DIAMETER protocol stack at a DIAMETER applicationlayer upon which the DIAMETER application operates, a transport layer,and an IP layer to ensure that transport resources are allocated to meetthe DIAMETER signaling requirement for the service.
 7. The universalDIAMETER orchestrator of claim 1, wherein the operations furthercomprise creating a map of DIAMETER resources available in the evolvedpacket core network to provide the service.
 8. A computer-readablestorage medium having instructions of a universal DIAMETER orchestratorstored thereon that, when executed by a processor, cause the processorto perform operations comprising: identifying a service of an evolvedpacket core network to be provided to a user equipment device; selectingDIAMETER peer nodes operating in a source domain and a destinationdomain of the evolved packet core network to support DIAMETER signalingtraffic associated with the service, wherein the DIAMETER peer nodesshare a direct transport connection between the source domain and thedestination domain of the evolved packet core network; and allocatingDIAMETER resources within the evolved packet core network to support theDIAMETER signaling traffic between the DIAMETER peer nodes over thedirect transport connection.
 9. The computer-readable storage medium ofclaim 8, wherein the operations further comprise receiving, from aservice application, a service request specifying the service to beprovided to the user equipment device.
 10. The computer-readable storagemedium of claim 8, wherein the DIAMETER signaling traffic between theDIAMETER peer nodes is routed through a DIAMETER agent of the DIAMETERresources within the evolved packet core network.
 11. Thecomputer-readable storage medium of claim 8, wherein the operationsfurther comprise allocating at least a portion of transport resources tocreate the direct transport connection between the DIAMETER peer nodes.12. The computer-readable storage medium of claim 8, wherein theoperations further comprise: determining a DIAMETER application to beutilized to meet a DIAMETER signaling requirement of the service,creating a structured representation of DIAMETER application dataassociated with the DIAMETER application, and reporting the structuredrepresentation to integrate with a network analytics engine.
 13. Thecomputer-readable storage medium of claim 12, wherein the operationsfurther comprise analyzing a structured DIAMETER protocol stack at aDIAMETER application layer upon which the DIAMETER application operates,a transport layer, and an IP layer to ensure that transport resourcesare allocated to meet the DIAMETER signaling requirement for theservice.
 14. The computer-readable storage medium of claim 8, whereinthe operations further comprise creating a map of DIAMETER resourcesavailable in the evolved packet core network to provide the service. 15.A method comprising: identifying, by a universal DIAMETER orchestratorassociated with an evolved packet core network, a service of the evolvedpacket core network to be provided to a user equipment device;selecting, by the universal DIAMETER orchestrator, DIAMETER peer nodesoperating in a source domain and a destination domain of the evolvedpacket core network to support DIAMETER signaling traffic associatedwith the service, wherein the DIAMETER peer nodes share a directtransport connection between the source domain and the destinationdomain of the evolved packet core network; and allocating, by theuniversal DIAMETER orchestrator, DIAMETER resources within the evolvedpacket core network to support the DIAMETER signaling traffic betweenthe DIAMETER peer nodes over the direct transport connection.
 16. Themethod of claim 15, further comprising receiving, by the universalDIAMETER orchestrator, from a service application, a service requestspecifying the service to be provided to the user equipment device. 17.The method of claim 15, further comprising allocating, by the universalDIAMETER orchestrator, at least a portion of transport resources tocreate the direct transport connection between the DIAMETER peer nodes.18. The method of claim 15, further comprising: determining, by theuniversal DIAMETER orchestrator, a DIAMETER application to be utilizedto meet a DIAMETER signaling requirement of the service, creating, bythe universal DIAMETER orchestrator, a structured representation ofDIAMETER application data associated with the DIAMETER application, andreporting, by the universal DIAMETER orchestrator, the structuredrepresentation to integrate with a network analytics engine.
 19. Themethod of claim 18, further comprising: analyzing, by the universalDIAMETER orchestrator, a structured DIAMETER protocol stack at aDIAMETER application layer upon which the DIAMETER application operates,a transport layer, and an IP layer to ensure that transport resourcesare allocated to meet the DIAMETER signaling requirement for theservice.
 20. The method of claim 15, further comprising creating, by theuniversal DIAMETER orchestrator, a map of DIAMETER resources availablein the evolved packet core network to provide the service.